-
-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automate .NET Version Selection in build.ps1
#1452
base: develop
Are you sure you want to change the base?
Automate .NET Version Selection in build.ps1
#1452
Conversation
I just feel like this is overcomplicating the build process, when all we need to support is simply netstandard2.0, net8.0, and net9.0 (removing net6.0/PS7.2 now they're EOL). For something that will only be affected once a year, I just feel it's not required. That, and it still requires manual intervention anyway, in the csproj file and workflows. I'm happy for this to be the net9.0/PS7.5 bump, and net6.0/PS7.2 removal. |
Should I roll back to the previous code? |
I still feel this is way overengineering something that only takes ~10-20mins once a year to update; plus manually we can properly verify the version bump works, rather than get any nasty surprises. |
Ok, I'll drop the eol part |
build.ps1
Based on EOL Statusbuild.ps1
Description:
This update improves the build process by dynamically selecting the appropriate .NET versions to deliver binaries, . By automatically excluding unsupported .NET versions, the
build.ps1
script now ensures that only maintained versions are targeted for binary generation.Key Changes: